Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: Ark Analysis description: Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.
Ark Analysis
This skill helps you analyze the Ark codebase by cloning the repository and examining its contents.
When to use this skill
Use this skill when:
- User asks "how does X work in Ark?"
- User wants to understand Ark's architecture or implementation
- User needs to examine Ark source code, CRDs, or controllers
- User mentions analyzing the Ark repository
Quick start
Clone the Ark repository to a temporary location:
git clone git@github.com:mckinsey/agents-at-scale-ark.git /tmp/ark-analysis
cd /tmp/ark-analysis
Codebase structure
The Ark repository is organized as follows:
-
ark/- Kubernetes operator (Go)- Controllers managing AI resources
- Custom Resource Definitions (CRDs)
- Webhooks for validation
-
services/- Supporting services (Go, Python, TypeScript)postgres-memory/- Memory persistenceexecutor-langchain/- LangChain execution engineark-api/- REST APIark-evaluator/- Model evaluation
-
samples/- Example configurations (YAML)- Agent definitions and queries
- Multi-agent teams
- A2A server examples
-
docs/- Documentation site (Next.js)
Common analysis tasks
Find controllers
ls ark/internal/controller/
grep -r "Reconcile" ark/internal/controller/
Find CRDs
ls ark/config/crd/bases/
grep -r "kind: Agent" samples/
Find A2A implementations
find . -path "*/a2a*" -type f
grep -r "A2AServer" .
Search for specific features
# Use ripgrep or grep to search
rg "query controller" --type go
grep -r "team coordination" --include="*.go"
Best practices
- Clone to /tmp: Always clone to
/tmp/ark-analysisto avoid cluttering the workspace - Navigate first:
cd /tmp/ark-analysisbefore running analysis commands - Use search tools: Prefer
rg(ripgrep) orgrepfor code searches - Check CLAUDE.md: Look for project-specific guidance in
CLAUDE.mdfiles - Clean up: Optionally remove the temp directory when done:
rm -rf /tmp/ark-analysis
Example workflows
Analyzing a controller
git clone git@github.com:mckinsey/agents-at-scale-ark.git /tmp/ark-analysis
cd /tmp/ark-analysis
cat ark/internal/controller/query_controller.go
grep -r "ExecuteQuery" ark/internal/genai/
Understanding A2A integration
cd /tmp/ark-analysis
find samples/a2a -name "*.py"
cat samples/a2a/simple-agent/src/simple_a2a_server/main.py
cat docs/content/developer-guide/building-a2a-servers.mdx
Finding CRD specifications
cd /tmp/ark-analysis
ls ark/api/v1prealpha1/
cat ark/api/v1prealpha1/agent_types.go
More by mckinsey
View allRegenerate and debug types across the ARK stack (SDK, API, Dashboard). Use when fixing TypeScript type errors in ark-dashboard, updating types after CRD changes, regenerating types.ts from OpenAPI spec, debugging "Property does not exist on type" schema errors, or adding custom SDK functionality via overlays. Covers the full type pipeline from Kubernetes CRDs to TypeScript.
Guidance for developing the Ark Kubernetes operator. Use when modifying Go types, CRDs, controllers, or webhooks. Helps with CRD generation and Helm chart sync issues.
CVE research and security patch workflow for Ark. Provides CVE API integration, mitigation strategies, and security-focused PR templates. Works with research, analysis, and setup skills for comprehensive vulnerability fixing.
Resolve common penetration testing issues in Ark. Use when fixing security vulnerabilities from pentest reports, security audits, or OWASP Top 10 issues.
